Method and system for notifying resource capability of user equipment

ABSTRACT

The present disclosure describes method and system for notifying resource capability of user equipment. In accordance with the embodiments, the method includes determining an event related to one or more multimedia multicast-broadcast service (MBMS) service of interest to the UE in receive only mode (ROM) session when a system information related to MBMS is not broadcasted by a serving cell after transmission of an interest indication for MBMS service to the serving cell wherein the event indicates one of: (a) the UE is not interested in the one or more MBMS service through the ROM session; and (b) the UE is not in reception of the one or more MBMS service through the ROM session; and transmitting a ROM service interest indication for the one or more MBMS service through the ROM session corresponding to the determined event to the serving cell.

RELATED APPLICATIONS

This application claims priority to Indian Provisional PatentApplication No. 201941006101 filed on Feb. 15, 2019, and Indian PatentApplication No. 201941006101 filed on Feb. 12, 2020, the entire contentsof each of which are incorporated herein by reference.

FIELD

The present disclosure generally relates to Multimedia BroadcastMulticast Service (MBMS). The present disclosure particularly relates tomethod and system for notifying baseband resource capability of userequipment.

BACKGROUND

The 3rd Generation Partnership Project (3GPP) provides for MultimediaBroadcast/Multicast Service (MBMS), which is a service of simultaneouslytransmitting a data packet to a plurality of users. The MBMS uses ashared channel so that a plurality of user equipment (UEs) efficientlyreceives data on one service. A base station allocates only one sharedchannel for data on one service, instead of allocating as many dedicatedchannels as the number of UEs to receive the service in one cell. Theplurality of UEs simultaneously receives the shared channel, thusimproving the efficiency of radio resources. A further development ofMBMS is evolved Multimedia Broadcast Multicast Services (eMBMS) whichprovide MBMS over Long Term Evolution (LTE) networks at LTE speeds. NowMBMS services can be delivered in three modes, i.e., a broadcast mode, amulticast mode, and unicast mode. In the broadcast mode, each UE canreceive the information within a service area on a unidirectionalchannel shared among the UEs. In the multicast mode, only the UE havinga subscription to the MBMS service can receive the information on theunidirectional channel. In the unicast mode, the UE can receive andtransmit data on dedicated bidirectional channels.

5^(th) Generation (5G) broadcast mode Further evolved MultimediaBroadcast Multicast Service (FeMBMS) is a further development orenhancement of LTE broadcast evolved Multimedia Broadcast MulticastServices (eMBMS). The radio interface enhancements introduced under 3GPPRelease 14/15 for FeMBMS include, dedicated broadcast transmission modeon a separate carrier with an Orthogonal Frequency-Division Multiplexing(OFDM) Cyclic Prefix (CP) length of up to 200 μs to support widecoverage areas (inter-site distance (ISD) upto 100 KM); flexible use ofnetwork capacity using up to 100% broadcast resource allocation forMBMS; shared eMBMS network for higher deployment flexibility; and newtype of Multicast-broadcast single-frequency network (MBSFN) subframewithout unicast control region to reduce overhead in dedicated broadcasttransmissions. This enables broadcasters to transmit FeMBMS via existingHigh Tower, High Power (HTHP) infrastructure targeting widespread reachfor TV services across masses (Free-to-Air, Free-to-View, Subscribedservices). The system layer enhancements introduced under 3GPP Release14/15 for FeMBMS include devices supporting Receive only Mode (ROM)session and devices supporting both MBMS and unicast with multiplereceivers (Rx). ROM session enables devices or user equipment's (UEs)without a SIM card or 3GPP subscription to access a subset of the 3GPPeMBMS TV services. Certain ROM enabled UEs are only capable of MBMSreception.

Now, baseband resource capability of the UE is affected with FeMBMSservices in ROM session. The baseband resource capability in generalrefers to processing and/or computational capability of the UE and canalso include maximum size of DFT/FFT, maximum power consumption, maximumthroughput, maximum number of scheduled entities or modules pertransmission timing interval (TTI), maximum number of scheduled physicalresource blocks (PRBs), and maximum number of physical channels. FeMBMSservices can use 7.5 KHz and 1.25 KHz sub-carrier spacing (SCS). In somecases, time division multiplexing (TDM) of the services with differentSCS is also possible. With full bandwidth and lower SCS, the UE needshigher computational capability. For example, Discrete Fourier Transform(DFT) size increases 2 times and 12 times for 7.5 KHz & 1.25 KHz SCS,respectively.

Further, the UE cannot support unicast operation with same basebandresource capability. As such, Carrier Aggregation (CA) configurationneeds to be handled by evolved NodeB (eNB) accordingly. Further, the eNBhandling unicast and the eNB providing FeMBMS services in the ROMsession may belong to different PLM/networks/operators and have nocoordination with each other.

Further, dynamic baseband resource capability information needs to besignaled by the UE. Considering, the UE signals maximum supportedbandwidth T and scaling factors A^((1.25) & A^((7.5), the CAconfiguration has to meet constraints as provided by the equation (1)T>Σ _(c=1) ^(C)(R _(c) B _(c) I _(c) ^((15kHz) +A ^((7.5) B _(c) I _(c)^((7.5kHz) +A ^((1.25) B _(c) I _(c) ^((1.25kHz))  (1)

Where C is the total number configured carrier components for the UE,B_(c) is the bandwidth for carrier c given in number of physicalresource blocks, R_(c) is the number of spatial layers supported bycarrier c and I_(c) ^((xKHz)=1 if carrier c is x KHz sub-carrier spacingand 0 otherwise.

The UE can report bandwidth (BW), Absolute Radio Frequency ChannelNumber (ARFCN), and SCS, as per the ROM session to account for reductionin UE's baseband resource capability and resultant CA configuration tobe applied by the eNB. However, baseband resource capability is regainedby the UE in the case when there is complete stop/loss of receptionand/or interest in FeMBMS services by the UE in the ROM session. Theresultant gain in baseband resource capability is not indicated by UE tothe eNB. This results in degraded performance due to inferior CAconfiguration still applicable to the UE.

Further, triggers related to both legacy MBMS services and FeMBMSservices in ROM session causes a complete list of services interestindications, which pertain to both the legacy MBMS services and theFeMBMS services in ROM session, to be communicated each time. This leadsto excessive signaling traffic on reverse link per UE for the eNB. TheeNB has no control over the signaling traffic as ROMfrequencies/services/triggers are controlled by the UE or other eNB.Furthermore, prioritization or no-prioritization possibilities for theROM services with respect to unicast services are not defined. As such,the UE misses the capability and option to control the prioritizationand user service experience.

Thus, it would be desirable to provide a solution that can overcome theabove-mentioned deficiencies.

SUMMARY

This summary is provided to introduce a selection of concepts in asimplified format that is further described in the detailed descriptionof the present disclosure. This summary is not intended to identify keyor essential inventive concepts of the claimed subject matter, nor is itintended for determining the scope of the claimed subject matter. Inaccordance with the purposes of the disclosure, the present disclosureas embodied and broadly described herein describes to method and systemfor notifying baseband resource capability of user equipment.

In accordance with some example embodiments of the inventive concepts, amethod of notifying resource capability of user equipment is disclosed.The method includes determining an event related to one or moremultimedia multicast-broadcast service (MBMS) service of interest to theUE in receive only mode (ROM) session when a system information relatedto MBMS is not broadcasted by a serving cell after transmission of aninterest indication for MBMS service to the serving cell. The eventindicates one of: (a) the UE is not interested in the one or more MBMSservice through the ROM session; and (b) the UE is not in reception ofthe one or more MBMS service through the ROM session. The methodincludes transmitting a ROM service interest indication for the one ormore MBMS service through the ROM session corresponding to thedetermined event to the serving cell.

In accordance with some example embodiments of the inventive concepts, asystem for notifying resource capability of user equipment is disclosed.The system includes at least one processor configured to executecomputer readable instructions to determine an event related to one ormore multimedia multicast-broadcast service (MBMS) service of interestto the UE in receive only mode (ROM) session when a system informationrelated to MBMS is not broadcasted by a serving cell after transmissionof an interest indication for MBMS service to the serving cell. Theevent indicates one of: (a) the UE is not interested in the one or moreMBMS service through the ROM session; and (b) the UE is not in receptionof the one or more MBMS service through the ROM session. The at leastone processor configured to execute computer readable instructions totransmit a ROM service interest indication for the one or more MBMSservice through the ROM session corresponding to the determined event tothe serving cell.

Some advantages of the present disclosure include, but not limited to,enabling notifying resource capability of the UE to the serving cell byway of transmitting the interest in one or more MBMS service through theROM session. This leads to improved performance as the serving cell isable to apply updated CA configuration based on the resource capabilityof the UE.

These aspects and advantages will be more clearly understood from thefollowing detailed description taken in conjunction with theaccompanying drawings and claims.

BRIEF DESCRIPTION OF THE DRAWINGS

These and other features, aspects, and/or advantages of the presentdisclosure will become better understood when the following detaileddescription is read with reference to the accompanying drawings in whichlike characters represent like parts throughout the drawings, wherein:

FIG. 1 illustrates an example wireless network depicting transmission ofthe Multimedia Broadcast Multicast Services (MBMS) service.

FIG. 2 illustrates an example wireless network depicting transmission ofthe Further evolved Multimedia Broadcast Multicast Services (FeMBMS)service.

FIG. 3 illustrates an example diagram of use of an MBMS interestindication message.

FIG. 4 illustrates an example diagram of use of interest indicationaccording to the present disclosure.

FIG. 5 illustrates an example block diagram of user equipment employinga system to notify the resource capability according to the presentdisclosure.

FIG. 6 illustrates an example block diagram of the system to notify theresource capability according to the present disclosure.

FIG. 7A & FIG. 7B to FIG. 9 illustrates an example diagram of use ofinterest indication message(s) according to the present disclosure.

FIG. 10 is a schematic diagrams illustrating data flow between networkelements, according to an embodiment of the present invention;

FIG. 11 illustrate flow diagram of method for activating input mode on avoice assistant device, in accordance with some example embodiments ofthe inventive concepts.

Further, skilled artisans will appreciate that elements in the drawingsare illustrated for simplicity and may not have been necessarily beendrawn to scale. For example, the flow charts illustrate the method interms of some operations involved to help to improve understanding ofaspects of the present disclosure. Furthermore, in terms of theconstruction of the device, one or more components of the device mayhave been represented in the drawings by conventional symbols, and thedrawings may show some specific details that are pertinent tounderstanding some example embodiments of the inventive concepts so asnot to obscure the drawings with details that will be readily apparentto those of ordinary skill in the art having benefit of the descriptionherein.

DETAILED DESCRIPTION

For the purpose of promoting an understanding of the principles of thedisclosure, reference will now be made to some example embodimentsillustrated in the drawings and specific language will be used todescribe the same. It will nevertheless be understood that no limitationof the scope of the disclosure is thereby intended, such alterations andfurther modifications in the illustrated system, and such furtherapplications of the principles of the disclosure as illustrated thereinbeing contemplated as would normally occur to one skilled in the art towhich the disclosure relates. Unless otherwise defined, all technicaland scientific terms used herein have the same meaning as commonlyunderstood by one of ordinary skilled in the art to which thisdisclosure belongs. The system, methods, and examples provided hereinare illustrative only and not intended to be limiting. Embodiments ofthe present disclosure will be described below in detail with referenceto the accompanying drawings.

FIG. 1 illustrates an example wireless network 100 depictingtransmission of the Multimedia Broadcast Multicast Services (MBMS)service. Examples of the MBMS services include but not limited to a newsservice, a sports service, video service, etc. The wireless network 100includes user equipment (UE) 102, network node 104, and a network core106. The UE 102 can be in communication with the network node 104. Thenetwork node 104 can be any of eNodeB, eNB, gNodeB, gNB, edge node. Thenetwork node 104 can be in communication with other network nodes (notshown in the figure) and Multicast Coordination Entity (MCE) (not shownin the figure). The MCE allocates time/frequency radio resources for theMBMS services, and determines the radio configuration (e.g., amodulation and coding scheme (MCS)) for the MBMS services. The networknode 104 may be connected with content provider 108 to provide directlyMBMS services to the UE 102. The MBMS services can be provided atdifferent frequencies. In addition, the UE 102 can be connected withother network nodes (not shown in the figure) to obtain MBMS services atother frequencies.

The network node 104 may be connected with the network core 106 (fore.g., Evolved Packet Core (EPC)) to provide access point to the networkcore 106 to the UE 102. The network core 106 can include variousentities such as Mobility Management Entity (MME), Multimedia BroadcastMulticast Service (MBMS) Gateway, a Broadcast Multicast Service Center(BM-SC), and a Packet Data Network (PDN) Gateway, etc., to provide MBMSservices to the UE 102. The network core 106 may be connected with IPservices 110 so as to connect with a content service 112 to provide MBMSservices to the UE 102. The UE 102 can receive the MBMS service inunicast mode (represented by dashed bidirectional line & referencecharacter ‘U’) or broadcast/multicast mode (represented by solidunidirectional line & reference character ‘M’). In the unicast mode, theUE 102 can receive and transmit data on dedicated bidirectional channel.In the broadcast mode, the UE 102 can receive the information on ashared unidirectional channel. In the multicast mode, the UE 102 havinga subscription to the MBMS service can receive the information on theshared unidirectional channel.

FIG. 2 illustrates an example wireless network 200 depictingtransmission of the Further evolved Multimedia Broadcast MulticastServices (FeMBMS) service. In the example, the UE 102 may be enabled inreceive only mode (ROM) with or without independent unicast. The ROM isenabled in the UE 102 using implementation-specific means (e.g. factoryconfiguration, user interface). As would be understood, the ROM enableduser equipment's are capable of accessing a subset of the 3GPP eMBMS TVservices without a SIM card or 3GPP subscription. Certain ROM enableduser equipment's are only capable of MBMS reception.

In an example, the UE 102 enabled in ROM without independent unicast canonly receive MBMS service and is not capable of establishing unicastconnectivity to receive unicast services. Examples of the unicastservices include voice call services, video call services, etc. As such,the UE 102 may be connected to cell(s) 202 capable of providing one ormore MBMS services in ROM session. The cell(s) 202 may be connected witha network core 204 (for e.g., Evolved Packet Core (EPC)) of a firstoperator through radio access network (RAN) 206 to provide one or moreMBMS services in ROM session (or FeMBMS services in ROM session) to theUE 102.

In another example, the UE 102 enabled in ROM with independent unicastcan receive MBMS service and is also capable of establishingunicast/multicast connectivity. As such, the UE 102 may be furtherconnected to cell(s) 208 capable of providing one or more legacy MBMSservices (i.e., MBMS services received when the UE is not in ROMsession) in unicast or broadcast/multicast mode. The cell(s) 208 may beconnected with a network core 210 (for e.g., Evolved Packet Core (EPC))of a second operator through legacy radio access network (RAN) 212 toprovide one or more legacy MBMS services and unicast services to the UE102.

Typically, the UE 102 in a connected mode (for e.g., in RRC connectedstate) may send an MBMS interest indication message to serving cell(s)to indicate a list of frequencies of interest to the UE 102. The UE maydetermine frequency of interest from a system information message, fore.g., system information block (SIB) 15 message, received from theserving cell(s). Accordingly, FIG. 3 illustrates an example diagram ofuse of an MBMS interest indication message. The example diagramillustrates communication between the UE 102 and the cell 208. At 302,the cell 208 sends a system information message, for e.g., SIB15message, to the UE 102 indicating a list of neighboring frequencies anda list of current frequencies, where each frequency in the list includesa list of MBMS service area identities (SAIs) supported by a respectivefrequency.

At 304, the UE 102 generates and sends a MBMS interest indicationmessage listing at least one frequency of interest and/or at least onealternative frequency of interest. However, baseband resource capabilityof the UE 102 is affected with MBMS service(s) in ROM session. Thebaseband resource capability in general refers to processing and/orcomputational capability of the UE and can also include maximum size ofDFT/FFT, maximum power consumption, maximum throughput, maximum numberof scheduled entities or modules per transmission timing interval (TTI),maximum number of scheduled physical resource blocks (PRBs), and maximumnumber of physical channels The baseband resource capability is regainedby the UE 102 in the case when there is complete stop/loss of receptionand/or interest in MBMS service(s) in ROM session by the UE 102 in theROM session. The resultant gain in baseband resource capability is notindicated by UE 102 to the serving cell 208.

In accordance with the embodiments of the present disclosure, the UE 102notifies resource capability to serving cell 208 when there is completestop/loss of reception and/or interest in MBMS service(s) in ROMsession. Accordingly, FIG. 4 illustrates an example diagram of use ofinterest indication according to the present disclosure. At 402, the UE102 determines an event related to one or more MBMS service of interestto the UE 102 in ROM session when user equipment information related toMBMS service, for e.g., SIB2 message, is not broadcasted by the cell 208after transmission of an interest indication for MBMS service to thecell 208. The event indicates one of: (a) the UE 102 is not interestedin the one or more MBMS service through the ROM session; and (b) the UE102 is not in reception of the one or more MBMS service through the ROMsession. At step 404, the UE 102 transmits a ROM service interestindication for the one or more MBMS service through the ROM sessioncorresponding to the determined event to the serving cell 208.

FIG. 5 illustrates an example block diagram of the UE 102 employing asystem 502 to notify the resource capability according to the presentdisclosure. The UE 102 may further include a processor 504, a memory506, and a transceiver 508. The system 502, the processor 504, thememory 506, and the transceiver 508 may be communicatively coupled witheach other via a bus (illustrated using directional arrows). Thetransceiver 508 is coupled to one or more antennas 510. The transceiver508 provides a mechanism for communicating with the cell 202 and thecell 208 over a transmission medium.

The processor 504 may be a single processing unit or a number of units,all of which could include multiple computing units. The processor 504may be implemented as one or more microprocessors, microcomputers,microcontrollers, digital signal processors, central processing units,processor cores, multi-core processors, multiprocessors, state machines,logic circuitries, application-specific integrated circuits, fieldprogrammable gate arrays and/or any devices that manipulate signalsbased on operational instructions. Among other capabilities, theprocessor 504 may be configured to fetch and/or executecomputer-readable instructions and/or data stored in the memory 506.

The memory 506 may include any non-transitory computer-readable mediumknown in the art including, for example, volatile memory, such as staticrandom access memory (SRAM) and/or dynamic random access memory (DRAM),and/or non-volatile memory, such as read-only memory (ROM), erasableprogrammable ROM (EPROM), flash memory, hard disks, optical disks,and/or magnetic tapes.

FIG. 6 illustrates an example block diagram of the system 502 to notifythe resource capability according to the present disclosure. The system502 includes a processor 602, a memory 604, and module(s) 606. Theprocessor 602, the memory 604, and the module(s) 606 may becommunicatively coupled with each other. The processor 602 may be asingle processing unit or a number of units, all of which could includemultiple computing units. The processor 602 may be implemented as one ormore microprocessors, microcomputers, microcontrollers, digital signalprocessors, central processing units, processor cores, multi-coreprocessors, multiprocessors, state machines, logic circuitries,application-specific integrated circuits, field programmable gate arraysand/or any devices that manipulate signals based on operationalinstructions. Among other capabilities, the processor 602 may beconfigured to fetch and/or execute computer-readable instructions and/ordata stored in the memory 602.

The memory 604 may include any non-transitory computer-readable mediumknown in the art including, for example, volatile memory, such as staticrandom access memory (SRAM) and/or dynamic random access memory (DRAM),and/or non-volatile memory, such as read-only memory (ROM), erasableprogrammable ROM (EPROM), flash memory, hard disks, optical disks,and/or magnetic tapes.

In an embodiment, the module(s) 606 may include a determination module608, a transmission module 610, and a priority module 612. Thedetermination module 608, the transmission module 610, and the prioritymodule 612 may be in communication with each other. The operationsdescribed herein can be performed by any of the system 502, theprocessor 504, the determination module 608, the transmission module610, and the priority module 612.

In accordance with the present embodiments, FIG. 7A illustrates anexample diagram of use of interest indication message(s) according tothe present disclosure. At 702, the determination module 608 determinesan event related to one or more MBMS service of interest to the UE 102in ROM session when user equipment information related to MBMS service,for e.g., SIB2 message, is not broadcasted by the cell 208 aftertransmission of an interest indication for MBMS service to the cell 208.In an implementation, the event indicates one of: (a) the UE 102 is notinterested in the one or more MBMS service through the ROM session; and(b) the UE 102 is not in reception of the one or more MBMS servicethrough the ROM session. The determination module 608 may determine lossof interest or reception based on signal quality measurements of a listof carrier frequencies supported by the serving cell 202 to provide theone or more MBMS service through the ROM session. The signal qualitymeasurements can be Reference Signal Receive Power (RSRP) or RSRQmeasurement and may be based on at least one of a Multimedia Broadcastmulticast service Single Frequency Network (MBSFN) RSRP measurement, oran MBSFN RSRQ measurement.

In an implementation, the determination module 608 determines the one ormore MBMS of interest in the ROM session when the UE 102 is in receptionof at least one MBMS in the ROM session. In an example of suchimplementation, the determination module 608 determines the event whenthe transmission module 210 did not transmit an MBMS Interest Indicationmessage since the UE 102 entered a connected mode, for e.g.,RRC_CONNECTED state. As would be understood, the UE 102 can reportfrequency(s) which provides a currently received or interested MBMSservice or frequency(s) which provides a no-longer received orinterested MBMS service to the cell 208 through the MBMS InterestIndication message.

In an implementation, the determination module 608 determines the one ormore MBMS of interest in the ROM session when the UE 102 is not inreception of the one or more MBMS through the ROM session. In an exampleof such implementation, the determination module 608 determines theevent when the determination module 608 did not receive systeminformation, for e.g., SIB15, broadcasted by the cell 202.

At step 704, the transmission module 610 transmits a ROM serviceinterest indication for the one or more MBMS service through the ROMsession corresponding to the determined event to the serving cell 208.The transmission module 610 transmits the ROM service interestindication based on the list of carrier frequencies supported by theserving cell 202. As such, the serving cell 202 sends the list offrequencies for which UE 102 is allowed to indicate MBMS interestindication message with respect to the MBMS services that UE 102 isreceiving and/or interested to receive in receive only mode on ROMsession to the determination module 608 and the transmission module 610.Therefore, the transmission module 610 cannot trigger or reportpertaining to other frequencies than the configured ones. This way theserving cell 202 controls the behavior of UE 102 and avoids unnecessary,irrelevant and frequent signaling from the UE 102.

Accordingly, at step 706, the transmission module 610 adds a ROM servicefield in a MBMS interest indication message to identify at least one ofthe ROM service interest indication, and a list of carrier frequenciessupporting the one or more MBMS service through the ROM session. At step708, the transmission module 610 adds an identifier in the MBMS interestindication message to identify a presence of at least one of the ROMservice field in the MBMS interest indication message and the list ofcarrier frequencies.

In some example embodiments, the event indicates the UE 102 is notinterested in or did not receive any MBMS services through the ROMsession. In other words, the UE 102 has complete stop (i.e., reception)or loss of interest in any of MBMS services. As such, the ROM servicefield can include a value ‘0’ for the MBMS services. Accordingly, theidentifier in the MBMS interest indication message indicates the ROMservice field has ‘0’ value.

At step 710, the transmission module 610 triggers a procedure forsending the MBMS interest indication message with the identifier and/orthe ROM service field identifying at least one of the ROM serviceinterest indication and the list of carrier frequencies to the cell 208.As such, the transmission module 610 prepares the MBMS interestindication message as described above and sends the MBMS interestindication message to the cell 208. In an example, the transmissionmodule 610 transmits the MBMS interest indication message to the cell208 through an MBMS radio bearer (MRB) or single cell point tomultipoint MBMS radio bearer (SC-MRB) when the UE 102 is in connectedmode (for e.g., in RRC connected state). The MBMS interest indicationmessage can be transmitted through a dedicated control channel (DCCH)which is a logical channel. A signaling radio bearer (SRB) for the MBMSinterest indication message is an SRB1, and the MBMS interest indicationmessage can be transmitted based on an acknowledgement mode (AM). In anexample, the transmission module 610 triggers a RACH procedure toestablish a connection with the cell 208 when the UE 102 is not in theconnected mode to transmit the MBMS interest indication message. Thus,the baseband resource capability is regained by the UE 102 when there iscomplete stop/loss of reception and/or interest in MBMS services in ROMsession is now indicated by the UE to the cell 208.

Referring to FIG. 7B, an example diagram for responding to an interestindication is illustrated. Accordingly, at step 712, the determinationmodule 608 receives a capability enquiry message from the serving cell208 in response to transmitting the ROM service interest indication atstep 710. At step 714, the determination module 608 determines acapability of the UE 102 in response to the capability enquiry message.The determination module 608 determines the capability of the UE 102using techniques as known in the art. At step 716, the transmittingmodule 610 transmits a capability message comprising information aboutthe capability of the UE 102 to the serving cell 208. The capabilityinformation comprises an RRC feature group indicator, indicating theMBMS and/or FeMBMS and/or ROM supported by the UE 102. At step 718, thedetermination module 608 receives the one or more MBMS through one oflegacy MBMS channel and a unicast channel from the serving cell 208 inresponse to transmitting the ROM service interest indication. Thus, theserving cell 208 is now able to apply optimum carrier aggregationconfiguration due to the baseband capability information sent by the UE102.

In some example embodiments, the UE 102 may be ROM enabled withindependent unicast. As such, the UE 102 may receive one or more MBMSservices in ROM session along with one or more legacy MBMS services.Accordingly, FIG. 8 illustrates an example diagram of use of interestindication message(s) according to the present disclosure. At step 802,the determination module 608 determines the event related to one or moreMBMS service of interest to the UE 102 in ROM session, as described atstep 702. At step 804, the determination module 608 determines aninterest of the UE 102 in one or more MBMS services in ROM session. Atstep 806, the determination module 608 determines an interest of the UE102 in one or more legacy MBMS services. The interest in MBMS servicesis determined based on user request or interest in particular serviceusing techniques as known in the art.

At step 808, the transmitting module 610 selectively transmits at leastone of legacy service interest indication about the interest of the UEin the one or more legacy MBMS service and a ROM service interestindication.

In one implementation, the UE 102 is having complete loss ofinterest/stop of MBMS services in ROM session while the UE 102 is havinginterest in legacy MBMS services. In one implementation, the UE 102 ishaving complete loss of interest/stop of both the MBMS services in ROMsession and the legacy MBMS services. In one implementation, the UE 102is having complete loss of interest/stop of in legacy MBMS serviceswhile the UE 102 is having interest MBMS services in ROM session.

In such implementations, at step 810, the transmitting module 610 addsat least one of a ROM service field and legacy service field in a MBMSinterest indication message. The ROM service field identifies at leastone of the ROM service interest indication and a list of carrierfrequencies supporting the one or more MBMS through the ROM session, asexplained earlier. The legacy service field identifies at least one ofthe legacy service interest indication and a list of carrier frequenciessupporting the one or more legacy MBMS, as known in the art.

At step 812, the transmitting module 610 adds an identifier in the MBMSinterest indication message to identify one of: an absence and apresence of one or more of: at least one of the ROM service field alongwith list of carrier frequencies supported by the cell 202 and thelegacy service field along with list of carrier frequencies supported bythe cell 208.

At step 814, the transmitting module 610 triggers a procedure forsending the MBMS interest indication message with the ROM service fieldidentifying at least one of the ROM service interest indication and thelist of carrier frequencies supporting the supporting the one or moreMBMS through the ROM session to the cell 208. The transmitting module610 triggers the procedure for sending the MBMS interest indicationmessage as explained at step 710.

Now, in one implementation, the UE 102 is having complete loss ofinterest/stop of MBMS services in ROM session while the UE 102 is havinginterest in legacy MBMS services. As such, the transmitting module 610triggers the procedure for sending the MBMS interest indication messagewith the ROM service field only at step 814. In another implementation,the UE 102 is having complete loss of interest/stop of MBMS services inROM session and in legacy MBMS services. As such, the transmittingmodule 610 triggers the procedure for sending the MBMS interestindication message with the ROM service field and the legacy servicefield. Accordingly, at step 814, the transmitting module 610 triggersthe procedure for sending the MBMS interest indication message with theROM service field and the legacy service field identifying at least oneof the legacy service interest indication and the list of carrierfrequencies supporting the supporting the one or more legacy MBMS to thecell 208. The transmitting module 610 triggers the procedure for sendingthe MBMS interest indication message as explained at step 710. In oneimplementation, there are no changes in interest of the UE 102 in MBMSservices in ROM session and/or in legacy MBMS services. In suchimplementation, the transmission module 610 transmits the MBMS interestindication message as known in the art.

Thus, the triggers related to both legacy MBMS services and MBMSservices in ROM session causes only a selective interest or no interestin list of frequencies to be communicated to the cells. This reducessignalling load.

In some example embodiments, allocation of resources, channels, etc., tothe UE 102 receiving the MBMS services in ROM session and/or the legacyservices is based on a priority assigned to the MBMS services in ROMsession and/or the legacy services. Accordingly, FIG. 9 illustrates anexample diagram of use of interest indication message(s) according tothe present disclosure. At step 902, the determination module 608determines the event related to one or more MBMS service of interest tothe UE 102 in ROM session, as described at step 702.

At step 904, the priority module 612 determines a priority of the one ormore MBMS services through the ROM sessions. The priority is determinedbased on at least one of: a predefined settings, a user-input, one ormore services received by the UE 102, performance measurement of the UE102, and optimal performance criteria of the UE 102. In an example, thepredefined settings can explicitly or implicitly indicate one or morefrequencies have higher priority. In such example, the predefinedsettings can be stored in the memory and the priority module 612 canfetch the predefined settings from the memory. In an example, thepriority module 612 may provide a notification on the UE 102 to receivethe user input. In an example, the priority module 612 may obtain signalquality measurements of a list of carrier frequencies supported by theserving cell 202 and the serving cell 208, power measurements (for e.g.,battery status) of the UE 102, bandwidth measurements of the UE 102,concurrent data sessions of the UE 102 in progress, and varioussubscriptions allotted to the UE 102. The signal quality measurementscan be RSRP/RSRQ measurement and may be based on at least one of anMBSFN RSRP measurement, or an MBSFN RSRQ measurement. In an example, thepriority module 612 may evaluate the signal quality measurements, powermeasurements, bandwidth measurements, concurrent data sessions inprogress, and subscriptions on the optimal performance criteria. Theoptimal performance criteria can indicate low power consumption, higherbandwidth requirement, higher charges of usage, low signal, etc.

In some example embodiments, the priority module 612 determines apriority of one or more legacy MBMS services. The priority of the legacyMBMS services is also determined based on at least one of: a predefinedsettings, a user-input, one or more services received by the UE 102,performance measurement of the UE 102, and optimal performance criteriaof the UE 102, as explained above. The priority module 612 thendetermines the priority of one or more MBMS services through the ROMsessions relative to the priority of the one or more legacy MBMSservices. In an example, the priority of MBMS services in ROM sessioncan be lower than a priority of legacy MBMS services.

At step 906, the transmitting module 610 transmits informationindicative of the determined priority in conjunction with the ROMservice interest indication. In an implementation, the priorityindicates the UE 102 is not interested in the one or more MBMS throughthe ROM session due to the performance measurements evaluated on theperformance criteria. For e.g., the UE 102 is not prioritizing MBMSservices in ROM sessions due to the need of additional resources. Insuch implementation, the transmitting module 610 only transmits the ROMservice interest indication with ‘0’ interest in MBMS services in ROMsession.

In one implementation, the priority indicates the UE 102 is interestedin the one or more MBMS through the ROM session. Accordingly, at step908, the transmitting module 610 adds the ROM service field in a MBMSinterest indication message to identify at least one of the ROM serviceinterest indication and a list of carrier frequencies supporting the oneor more MBMS through the ROM session, as described at step 704.

At step 910, the transmitting module 610 extends a priority field in theMBMS interest indication message to indicate the priority of one or moreMBMS services through the ROM sessions. Typically, a priority field inthe MBMS interest indication message indicates whether reception oflegacy MBMS services is prioritized over unicast reception by the UE102. According to the present invention, the UE 102 can now reportwhether reception of legacy MBMS services excluding MBMS services in ROMsession is prioritized over unicast reception through the priority fieldin MBMS interest indication message. Additionally the priority field inthe MBMS interest indication message indicates whether reception oflegacy MBMS services is prioritized over ROM services or vice-versa.

At step 912, the transmitting module 610 triggers a procedure forsending the MBMS interest indication message with the ROM service fieldand the extended priority field, as explained in step 704.

The following section now illustrates the example procedure taken by theUE 102 in accordance with the above embodiments. The purpose of thisprocedure is to inform E-UTRAN (i.e., the cell 208) that the UE 102 isreceiving or is interested to receive MBMS service(s) via an MRB orSC-MRB, and if so, to inform the E-UTRAN about the priority of MBMSversus unicast reception or MBMS service(s) reception in ROM session.

Section 1: Initiation

An MBMS or SC-PTM capable UE in RRC_CONNECTED may initiate the procedurein several cases including:

-   -   (1) upon successful connection establishment;    -   (2) upon entering or leaving the service area;    -   (3) upon session start or stop;    -   (4) upon change of interest;    -   (5) upon change of priority between MBMS reception and unicast        reception;    -   (6) upon change to a PCell broadcasting        SystemInformationBlockType15;    -   (7) upon starting and stopping of MBMS service(s) in ROM; and    -   (8) upon change of receive only mode (ROM) frequency, bandwidth        (BW), or subcarrier spacing (SCS) of MBMS service(s) in ROM.        Upon initiating the procedure, the UE shall:    -   1> if SystemInformationBlockType15 is broadcast by the PCell; or    -   1> if mbms-ROM-ServiceIndication is received in        SystemInformationBlockType2 from PCell:        -   2> ensure having a valid version of            SystemInformationBlockType15 for the PCell, if present;        -   2> if the UE did not transmit an MBMSInterestIndication            message since last entering RRC_CONNECTED state; or        -   2> if since the last time the UE transmitted an            MBMSInterestIndication message, the UE connected to a PCell            neither broadcasting SystemInformationBlockType15 nor            including mbms-ROM-ServiceIndication in            SystemInformationBlockType2:            -   3> if the set of MBMS frequencies of interest,                determined in accordance with Section 2 described below,                is not empty:                -   4> initiate transmission of the                    MBMSInterestIndication message in accordance with                    Section 3 described below;        -   2> else:            -   3> if the set of MBMS frequencies of interest,                determined in accordance with Section 2 described below,                has changed since the last transmission of the                MBMSInterestIndication message; or            -   3> if at least one of the subcarrier spacing or                bandwidth parameter of receive only mode MBMS frequency                of interest, determined in accordance with Section 2                described below, has changed since the last transmission                of the MBMSInterestIndication message; or            -   3> if the prioritisation of reception of all indicated                MBMS frequencies (excluding those pertaining to receive                only mode) compared to reception of any of the                established unicast bearers has changed since the last                transmission of the MBMSInterestIndication message:                -   4> initiate transmission of the                    MBMSInterestIndication message in accordance with                    Section 3 described below;                -   In one of the embodiments of the present disclosure,                    the UE provides user level prioritization for ROM                    services or incorporate prioritization for ROM                    services at par with legacy MBMS. To this end, MBMS                    priority field is extended to incorporate ROM                    services as well.            -   3> else if SystemInformationBlockType20 is broadcast by                the PCell:                -   4> if since the last time the UE transmitted an                    MBMSInterestIndication message, the UE connected to                    a PCell not broadcasting                    SystemInformationBlockType20;                -   or                -   4> if the set of MBMS services of interest                    determined in accordance with Section 2a described                    below is different from mbms-Services included in                    the last transmission of the MBMSInterestIndication                    message;        -   5> initiate the transmission of the MBMSInterestIndication            message in accordance with Section 3 described below.            Section 2: Determine MBMS Frequencies of Interest            The UE shall:    -   1> consider a frequency to be part of the MBMS frequencies of        interest if the following conditions are met:        -   2> if at least one MBMS session the UE is receiving or            interested to receive via an MRB or SC-MRB is ongoing or            about to start; and        -   2> for at least one of these MBMS sessions either            SystemInformationBlockType15 acquired from the PCell            includes for the concerned frequency one or more MBMS SAIs            as indicated in the USD for this session; and        -   2> the UE is capable of simultaneously receiving MRBs and/or            is capable of simultaneously receiving SC-MRBs on the set of            MBMS frequencies of interest, regardless of whether a            serving cell is configured on each of these frequencies or            not; and        -   2> the supportedBandCombination the UE included in            UE-EUTRA-Capability contains at least one band combination            including the set of MBMS frequencies of interest;    -   2> if there is at least one MBMS session the UE is receiving        and/or interested to receive in receive only mode and the        supportedBandCombination the UE included in UE-EUTRA-Capability        contains at least one band combination including the set of MBMS        frequencies of interest for receive only mode;        Section 2a: Determine MBMS Services of Interest        The UE shall:    -   1> consider a MBMS service to be part of the MBMS services of        interest if the following conditions are met:        -   2> the UE is SC-PTM capable; and        -   2> the UE is receiving or interested to receive this service            via an SC-MRB; and        -   2> one session of this service is ongoing or about to start;            and        -   2> one or more MBMS SAIs in the USD for this service is            included in SystemInformationBlockType15 acquired from the            PCell for a frequency belonging to the set of MBMS            frequencies of interest, determined according to the Section            2 as described above.            Section 3: Actions Related to Transmission of            MBMSInterestIndication Message            The UE shall set the contents of the MBMSInterestIndication            message as follows:    -   1> if the set of MBMS frequencies of interest (excluding those        pertaining to receive only mode), determined in accordance with        Section 2 as described above, is not empty:        -   2> include mbms-FreqList and set it to include the MBMS            frequencies of interest sorted by decreasing order of            interest, using the EARFCN corresponding with            freqBandIndicator included in SystemInformationBlockType1            (for serving frequency), if applicable, and the EARFCN(s) as            included in SystemInformationBlockType15 (for neighbouring            frequencies);        -   2> include mbms-Priority if the UE prioritises reception of            all indicated MBMS above reception of any of the unicast            bearers;        -   2> if SystemInformationBlockType20 is broadcast by the            PCell:            -   3> include mbms-Services and set it to indicate the set                of MBMS services of interest determined in accordance                with Section 2a as described above;    -   1> if the UE is receiving MBMS service(s) in receive only mode:        -   2> if the supportedBandCombination the UE included in            UE-EUTRA-Capability contains at least one band combination            including the mbms-ROM-Freq:            -   3> include mbms-ROM-Freq, mbms-ROM-SubcarrierSpacing and                mbms-Bandwidth;    -   1> include triggerType:        -   2> set the least significant bit as 1 if mbms-ROM-InfoList            is changed from last transmission;        -   2> set the most significant bit as 1 if mbms-FreqList is            changed from last transmission;

Here triggerType indicates one or more triggers for theMBMSlnterestIndication. The least significant bit corresponds to the setof receive only mode frequencies and next bit corresponds to set ofother frequencies. A bit is set to 1 if the trigger happened because ofcorresponding set of frequencies is changed, and 0 otherwise.

In one of the embodiment of the present disclosure, it is possible tohave an implementation solution supporting triggerType field to doselective reporting MBMS interest information for legacy and ROM MBMSservices as well as another implementation solution where triggerTypefield is not used.

The UE shall submit the MBMSInterestIndication message to lower layersfor transmission.

Section 4: MBMSInterestIndication

The MBMSInterestIndication message is used to inform E-UTRAN that the UEis receiving/interested to receive or no longer receiving/interested toreceive MBMS via an MRB or SC-MRB including MBMS service(s) in receiveonly mode.

Table 1 illustrates an example of the MBMS interest indication messagewith the ROM service field, the legacy service field, and theidentifiers as explained above.

TABLE 1 -- ASN1START MBMSInterestIndication-r11 ::= SEQUENCE {criticalExtensions CHOICE { c1 CHOICE { interestIndication-r11MBMSInterestIndication-r11-IEs, spare3 NULL, spare2 NULL, spare1 NULL },criticalExtensionsFuture SEQUENCE { } } } MBMSInterestIndication-r11-IEs::= SEQUENCE { mbms-FreqList-r11 CarrierFreqListMBMS-r11 OPTIONAL,mbms-Priority-r11 ENUMERATED {true} OPTIONAL, lateNonCriticalExtensionOCTET STRING OPTIONAL, nonCriticalExtensionMBMSInterestIndication-v1310-IEs OPTIONAL }MBMSInterestIndication-v1310-IEs ::= SEQUENCE { mbms-Services-r13MBMS-ServiceList-r13 OPTIONAL, nonCriticalExtensionMBMSInterestIndication-v1540-IEs OPTIONAL }MBMSInterestIndication-v1540-IEs ::=  SEQUENCE { mbms-ROM-InfoList-r15SEQUENCE (SIZE(1..maxMBMS- ServiceListPerUE-r13)) OF MBMS-ROM-Info-r15OPTIONAL, nonCriticalExtension SEQUENCE { } OPTIONAL } MBMS-ROM-Info-r15::= SEQUENCE { mbms-ROM-Freq-r15 ARFCN-ValueEUTRA-r9,mbms-ROM-SubcarrierSpacing-r15 ENUMERATED {kHz15, kHz7dot5, kHz1dot25},mbms-Bandwidth-r15 ENUMERATED {n6, n15, n25, n50, n75, n100} } --ASN1STOP

In the above Table 1, the mbms-FreqList field indicates a list offrequencies which provide a legacy MBMS service currently received orinterested by the UE 102. The mbms-Priority field indicates whetherreception of legacy MBMS reception is prioritized over unicast receptionby the UE. In an implementation, a value of the mbms-Priority field istrue, if the UE prioritises reception of all listed MBMS frequencies,excluding the MBMS frequencies in the ROM session, over reception of anyof the unicast bearers. The exclusions are indicated by theMBMSInterestIndication-v1310 field. In an implementation, thembms-Priority field is omitted if the reception of all listed MBMSfrequencies is not prioritized.

The mbms-ROM-Freq field indicates the carrier frequency used by the UEto receive MBMS service(s) in ROM session. The mbms-ROM-InfoList fieldor the ROM service field indicates list of MBMS service(s) in ROMsession related parameters which the UE 102 is receiving. In oneimplementation, if the UE 102 is no longer receiving MBMS services(s) inROM, the mbms-ROM-InfoList is omitted. In one implementation, if the UE102 is no longer receiving MBMS services(s) in ROM, thembms-ROM-InfoList is set to ‘0’ value. The mbms-ROM-SubcarrierSpacingfield indicates subcarrier spacing for MBSFN subframes received by theUE 102 in ROM session. The presence of ROM service field is indicated bythe MBMSInterestIndication-v1540 field.

FIG. 10 is a network diagram 1000 illustrating data flow between networkelements, according to an embodiment of the present invention. Thenetwork comprises at least one of a EUTRAN, plurality of eNodeB, amanagement control entity (MCE), plurality of mobility management entity(MME), MBMS gateway MBMS-GW, plurality of primary gateway P-GW,plurality of secondary gateway S-GW, and a content provider. Duringcommunication between the EUTRAN and the content provider, data transfercan be performed over different network elements forming differentnetwork connection. During forming the network connection, one or morenetwork elements can be used as shared MBMS network elements, whileother can belong to PLMN network elements. Based on the interest on theMBMS services in ROM session, the UE can transmit the MBMS interestindication message as described earlier.

FIG. 11 illustrate flow diagram of method for activating input mode on avoice assistant device, in accordance with some example embodiments ofthe inventive concepts. The method 1100 may be implemented by the system502 and/or the UE 102, as described above. Further, for the sake ofbrevity, details of the present disclosure that are explained in detailsin the description of FIG. 1 to FIG. 9 are not explained in detail inthe description of FIG. 10.

At block 1102, the method 1100 includes determining an event related toone or more multimedia multicast-broadcast service (MBMS) service ofinterest to the UE in receive only mode (ROM) session when a systeminformation related to MBMS is not broadcasted by a serving cell aftertransmission of an interest indication for MBMS service to the servingcell The event indicates one of: (a) the UE is not interested in the oneor more MBMS service through the ROM session; and (b) the UE is not inreception of the one or more MBMS service through the ROM session.

At block 1104, the method 1100 includes transmitting a ROM serviceinterest indication for the one or more MBMS service through the ROMsession corresponding to the determined event to the serving cell. TheROM service interest indication includes at least one of identity of theone or more MBMS service and interest of the UE indicating one of: (a)the UE is not interested in the one or more MBMS service through the ROMsession; and (b) the UE is not in reception of the one or more MBMSservice through the ROM session. The transmitting of the ROM serviceinterest indication is based on a list of carrier frequencies supportedby the serving cell to provide the one or more MBMS service through theROM session.

In some example embodiments, the method 1100 includes determining theone or more MBMS of interest in the ROM session when one of: (a) the UEis in reception of at least one MBMS in the ROM session and (b) the UEis not in reception of the none or more MBMS through the ROM session.

Further, the step of transmitting the ROM service interest indication atblock 1004 comprises further steps. Accordingly, the method 1100includes adding a ROM service field in a MBMS interest indicationmessage to identify at least one of the ROM service interest indication,and a list of carrier frequencies supporting the one or more MBMSservice through the ROM session. The method 1100 includes triggering aprocedure for sending the MBMS interest indication message with the ROMservice field identifying at least one of the ROM service interestindication and the list of carrier frequencies. In some exampleembodiments, the method 1100 includes adding an identifier in the MBMSinterest indication message to identify a presence of at least one ofthe ROM service field in the MBMS interest indication message and thelist of carrier frequencies.

Further, in some example embodiments the method 1100 includes additionalsteps. Accordingly, the method 1100 includes determining an interest ofthe UE in one or more legacy MBMS. The method 1100 includes selectivelytransmitting at least one of legacy service interest indication aboutthe interest of the UE in the one or more legacy MBMS service and theROM service interest indication.

Further, in some example embodiments, the step of selective transmittingcomprises additional steps. Accordingly, the method 1100 includes addingin a MBMS interest indication message at least one of (a) a ROM servicefield to identify at least one of the ROM service interest indicationand a list of carrier frequencies supporting the one or more MBMSthrough the ROM session; and (b) a legacy service field to identify atleast one of the legacy service interest indication and a list ofcarrier frequencies supporting the one or more legacy MBMS.

The method 1100 includes adding an identifier in the MBMS interestindication message to identify one of: an absence and a presence of oneor more of: (a) at least one of the ROM service field and the list ofcarriers supporting the supporting the one or more MBMS through the ROMsession; and (b) at least one of the legacy service field and the listof carriers supporting the supporting the one or more legacy MBMS.

In some example embodiments, the step of selective transmittingcomprises triggering at least one procedure. Accordingly, in someembodiments, the method 1100 includes triggering a procedure for sendingthe MBMS interest indication message with the ROM service fieldidentifying at least one of the ROM service interest indication and thelist of carrier frequencies supporting the supporting the one or moreMBMS through the ROM session. In some embodiments, the method 1100includes triggering a procedure for sending the MBMS interest indicationmessage with the legacy service field identifying at least one of thelegacy service interest indication and the list of carrier frequenciessupporting the supporting the one or more legacy MBMS. In someembodiment, the method 1100 includes triggering the procedure forsending the MBMS interest indication message with the ROM service fieldand triggering the procedure for sending the MBMS interest indicationmessage with the legacy service field.

Further, in some example embodiments the method 1100 includes additionalsteps. Accordingly, the method 1100 includes determining a priority ofthe one or more MBMS services through the ROM sessions. The priority isdetermined based on at least one of: a predefined settings, auser-input, one or more services received by the UE, performancemeasurement of the UE, and optimal performance criteria of the UE. Thedetermined priority indicates one of (a) the UE is not interested in theone or more MBMS through the ROM session; and (b) the UE is interestedin the one or more MBMS through the ROM session. At block 1404, themethod 1100 includes transmitting information indicative of thedetermined priority in conjunction with the ROM service interestindication.

Further, in some example embodiments, the step of determining prioritycomprises additional step. Accordingly, the method 1100 includesdetermining a priority of one or more legacy MBMS services. The method1100 includes determining the priority of one or more MBMS servicesthrough the ROM sessions relative to the priority of the one or morelegacy MBMS services.

Further, in some example embodiments, the step of transmitting at block1404 includes additional steps. Accordingly, the method 1100 includesadding a ROM service field in a MBMS interest indication message toidentify at least one of the ROM service interest indication and a listof carrier frequencies supporting the one or more MBMS through the ROMsession. The method 1100 includes extending a priority field in the MBMSinterest indication message to indicate the priority of one or more MBMSservices through the ROM sessions. The method 1100 includes triggering aprocedure for sending the MBMS interest indication message with the ROMservice field and the extended priority field.

Further, in some example embodiments, the method 1100 includesadditional steps. Accordingly, the method 1100 includes receiving acapability enquiry message from the serving cell in response totransmitting the ROM service interest indication. The method 1100includes determining a capability of the UE in response to thecapability enquiry message. The method 1100 includes transmitting acapability message comprising information about the capability of the UEto the serving cell. The method 1100 includes receiving the one or moreMBMS through one of legacy MBMS channel and a unicast channel from theserving cell in response to transmitting the ROM service interestindication.

While specific language has been used to describe the presentdisclosure, any limitations arising on account thereto, are notintended. As would be apparent to a person in the art, various workingmodifications may be made to the method in order to implement theinventive concepts as taught herein. The drawings and the foregoingdescription give examples of embodiments. Those skilled in the art willappreciate that one or more of the described elements may well becombined into a single functional element. Alternatively, certainelements may be split into multiple functional elements. Elements fromone embodiment may be added to another embodiment. Clearly, the presentdisclosure may be otherwise variously embodied, and practiced within thescope of the following claims.

We claim:
 1. A method for resource capability notification by a userequipment (UE), the method comprising: determining an event related to amultimedia multicast-broadcast service (MBMS) service in a receive onlymode (ROM) session in response to UE information related to the MBMSservice not being broadcasted by a serving cell after transmission of afirst interest indication for the MBMS service to the serving cell, thefirst interest indication indicating that the MBMS service is ofinterest to the UE, and the event indicating one of, MBMS servicethrough the ROM session is not of interest to the UE, or the UE is notin reception of the MBMS service through the ROM session; andtransmitting a second interest indication for the MBMS service to theserving cell through the ROM session, the second interest indicationcorresponding to the event.
 2. The method as claimed in claim 1, whereinthe second interest indication includes at least one of an identity ofthe MBMS service or an interest of the UE, the interest of the UEindicating one of, MBMS service through the ROM session is not ofinterest to the UE, or the UE is not in reception of the MBMS servicethrough the ROM session.
 3. The method as claimed in claim 1, whereinthe transmitting the second interest indication comprises: adding a ROMservice field in a MBMS interest indication message to identify at leastone of a ROM service interest indication or a list of carrierfrequencies supporting the MBMS service through the ROM session; andtriggering a procedure for sending the MBMS interest indication messagewith the ROM service field.
 4. The method as claimed in claim 3, whereinthe transmitting the second interest indication comprises: adding anidentifier in the MBMS interest indication message to identify apresence of the ROM service field.
 5. The method as claimed in claim 1,wherein the transmitting the second interest indication is based on alist of carrier frequencies supported by the serving cell to provide theMBMS service through the ROM session.
 6. The method as claimed in claim1, further comprising: determining a legacy MBMS is of interest to theUE; and selectively transmitting at least one of a legacy serviceinterest indication or the second interest indication, the legacyservice interest indication indicating the legacy MBMS is of interest tothe UE.
 7. The method as claimed in claim 6, wherein the selectivelytransmitting comprises at least one of: adding a ROM service field in aMBMS interest indication message, the ROM service field identifying atleast one of a ROM service interest indication or a list of carrierfrequencies supporting the MBMS service through the ROM session; or alegacy service field in the MBMS interest indication message, the legacyservice field identifying at least one of the legacy service interestindication or a list of carrier frequencies supporting the legacy MBMS.8. The method as claimed in claim 7, wherein the selectivelytransmitting comprises: adding an identifier in the MBMS interestindication message, the identifier identifying an absence or a presenceof one or more of: the ROM service field; or the legacy service field.9. The method as claimed in claim 8, wherein the selectivelytransmitting comprises at last one of: triggering a procedure forsending the MBMS interest indication message with the ROM service field;or triggering a procedure for sending the MBMS interest indicationmessage with the legacy service field.
 10. The method as claimed inclaim 1, further comprising: determining a priority of the MBMS service;and transmitting information indicative of the priority in conjunctionwith the second interest indication.
 11. The method as claimed in claim10, wherein the determining the priority determines the priority basedon at least one of: a settings, a user-input, one or more servicesreceived by the UE, a performance measurement of the UE, or aperformance criteria of the UE.
 12. The method as claimed in claim 11,wherein the priority indicates one of: the MBMS through the ROM sessionis not of interest to the UE; or the MBMS through the ROM session is ofinterest to the UE.
 13. The method as claimed in claim 10, furthercomprising: determining a priority of one or more legacy MBMS services;and determining the priority of the MBMS service relative to thepriority of the one or more legacy MBMS services.
 14. The method asclaimed in claim 10, wherein the transmitting the second interestindication comprises: adding a ROM service field in a MBMS interestindication message to identify at least one of a ROM service interestindication or a list of carrier frequencies supporting the MBMS servicethrough the ROM session; extending a priority field in the MBMS interestindication message to indicate the priority; and triggering a procedurefor sending the MBMS interest indication message with the ROM servicefield and the priority field.
 15. The method as claimed in claim 1,further comprising: determining the event related to the MBMS servicewhen the UE is in reception of at least one MBMS in the ROM session orthe UE is not in reception of the MBMS service through the ROM session.16. The method as claimed in claim 1, further comprising: receiving acapability enquiry message from the serving cell in response totransmitting the second interest indication; determining a capability ofthe UE in response to the capability enquiry message; and transmitting acapability message to the serving cell, the capability message includinginformation about the capability.
 17. The method as claimed in claim 16,further comprising: receiving the MBMS service through one of a legacyMBMS channel or a unicast channel from the serving cell in response totransmitting the second interest indication.
 18. A system for resourcecapability notification by a user equipment (UE), the system comprising:at least one processor configured to execute computer readableinstructions to: determine an event related to a multimediamulticast-broadcast service (MBMS) service in a receive only mode (ROM)session in response to UE information related to the MBMS service notbeing broadcasted by a serving cell after transmission of a firstinterest indication for the MBMS service to the serving cell, the firstinterest indication indicating that the MBMS service is of interest tothe UE, and the event indicating one of, the MBMS service through theROM session is not of interest to the UE, or the UE is not in receptionof the MBMS service through the ROM session; and transmit a secondinterest indication for the MBMS service to the serving cell through theROM session, the second interest indication corresponding to the event.19. The system as claimed in claim 18, wherein the second interestindication includes at least one of an identity of the MBMS service oran interest of the UE, the interest of the UE indicating one of, theMBMS service through the ROM session is not of interest to the UE, orthe UE is not in reception of the MBMS service through the ROM session.20. The system as claimed in claim 18, wherein the at least oneprocessor is configured to execute computer readable instructions totransmit the second interest indication, including: adding a ROM servicefield in a MBMS interest indication message to identify at least one ofa ROM service interest indication or a list of carrier frequenciessupporting the MBMS service through the ROM session; and triggering aprocedure for sending the MBMS interest indication message with the ROMservice field.